Release 10.1A: OpenEdge Getting Started:
Core Business Services


Configuring SSL client sessions

Table 7–3 describes the SSL session properties that you can set for an OpenEdge SSL client.

Table 7–3: OpenEdge client SSL session properties
Property
Default setting
Description
Use SSL to connect
No
Specifies if the client connection uses SSL tunneling.
Reuse a disconnected SSL session
Yes
Specifies if the connection reuses a previously established and disconnected SSL session when the client connects to an SSL server.
Verify the SSL server host name
Yes
Indicates if the client compares the host name of the SSL server with the Common Name specified in the server digital certificate, and raises an error if they do not match. If this property is set to No, the client never raises the error. This can be a useful setting if SSL server identity is likely to be moved from one physical machine to another and you do not want this to interfere with making the connection.
Certificate store location (Java Open Client only)1
None
Specifies the location of the root certificate store used by the client for SSL connections.
1The certificate store for all OpenEdge-managed SSL clients, except the Java and .NET Open clients, is installed in the same location under the OpenEdge installation path for each OpenEdge SSL client. For Java Open Clients, there is no standard location for the certificate store, so you must manage it using the tools provided with the Open Client Toolkit and specify its location to configure Java Open Client SSL connections. For .NET Open Clients, you must locate and manage the certificate store as provided by the tools available with Microsoft .NET.

Table 7–4 describes the mechanisms for setting SSL session properties for OpenEdge SSL clients and indicates where you can find more information about them.

Table 7–4: Mechanisms for setting OpenEdge SSL client session
properties
This SSL client
component...
Relies on this mechanism...
To set its SSL properties as described in...
Progress 4GL database client
Startup and connection parameters.
Progress 4GL AppServer client1
Connection parameters (for the Internet using the AIA or an intranet).
Progress 4GL client of industry Web services1
Connection parameters.
Progress 4GL client of the SonicMQ BrokerConnect1
Connection parameters (for the Internet using the AIA or an intranet).
Progress 4GL socket client1
Connection parameters.
.NET Open Clients of the AppServer
Connection parameters and run-time properties (for the Internet using the AIA or an intranet).
Java Open Clients of the AppServer
Connection parameters and run-time properties (for the Internet using the AIA or an intranet).
JDBC or ODBC SQL database clients
Switches on the client connection string.
AppServer Internet Adapter (AIA)
The Progress Explorer framework.
Web Services Adapter (WSA)
The Progress Explorer properties editor for each Web service instance.
Sonic ESB Adapter
Sonic ESB tools for managing OpenEdge services.
WebSpeed Messenger
The Progress Explorer framework.
1The Progress 4GL in WebClient applications can also perform any of these SSL client functions in a user-downloadable application environment. However, note that the WebClient does not support access to any OpenEdge relational data source, including the OpenEdge RDBMS. The WebClient relies on the AppServer for all access to OpenEdge relational data sources. OpenEdge provides separate support for securely downloading and updating the WebClient and its application code over the Internet or an intranet. For more information, see OpenEdge Deployment: WebClient Applications .

Other client platforms potentially involved with OpenEdge SSL servers, including Web service clients of Progress 4GL Web services (managed by the WSA) and Web browser clients of WebSpeed, provide their own mechanisms for making SSL connections using HTTPS. For more information, see the platform documentation.


Copyright © 2005 Progress Software Corporation
www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095